Skip to content

Conversation

@masnwilliams
Copy link
Contributor

@masnwilliams masnwilliams commented Sep 11, 2025

TL;DR

Reordered the 'Get Started' pages in the documentation sidebar.

Why we made these changes

To improve the user journey by presenting the 'Get Started' topics in a more logical sequence, making the onboarding experience more intuitive for new users.

What changed?

  • Modified docs.json to update the sequence of pages under the 'Get Started' section.

Description generated by Mesa. Update settings

Copy link
Contributor

@mesa-dot-dev mesa-dot-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Performed full review of 2b8eea3...4b7ce85

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

Slash Commands:

  • /review - Request a full code review
  • /review latest - Review only changes since the last review
  • /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
  • /help - Get help with Mesa commands and configuration options

1 files reviewed | 1 comments | Review on Mesa | Edit Reviewer Settings

"pages": [
"introduction",
"quickstart"
"quickstart",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Medium Logic

Consider the user journey when reordering these pages. Typically, an 'introduction' page provides context and overview before users dive into a 'quickstart'. This reordering may confuse new users who jump straight into quickstart without understanding the fundamentals. Consider whether this aligns with your documentation strategy.
Agent: 🤖 General

@masnwilliams masnwilliams merged commit a1c9fd9 into main Sep 11, 2025
3 checks passed
@masnwilliams masnwilliams deleted the mason/test branch September 11, 2025 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants